Methods and systems for providing online verification and security

ABSTRACT

The methods and systems are designed to utilize an integrated combination of just in time, just in place, and just on device actions connected to an image recognition process to reduce or remove the risk of a User utilizing fake or stolen credentials in order to get verified.

CROSS-REFERENCED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 14/737,460, filed Jun. 11, 2015, issued as U.S. Pat. No.10,225,248 on Mar. 5, 2019, which claims priority to and all benefits ofprovisional patent application Ser. No. 62/010,567, filed Jun. 11, 2014,which is incorporated by reference herein.

BACKGROUND

As web traffic continues to increase, electronic identification thefthas been growing exponentially. Such electronic identification theft canoriginate from anywhere in the world. Electronic identification theftcosts many millions of dollars in losses and can have a lastingemotional effect on the victims. Accordingly, new methods and systemsfor providing online verification and security are needed.

SUMMARY

Various embodiments provide methods and systems for providing onlineverification and security. Some embodiments include methods forproviding a secured system.

For example, a method for providing a secured system can include thesteps of: taking a photograph of face at first location with a devicecomprising a clock and a GPS; tagging the photograph of face with GPScoordinates of the first location; tagging the photograph of face with atime and date of the taking the photograph of face; taking a photographof an identification card comprising a picture at a second location;tagging the photograph of an identification card with GPS of the secondlocation; tagging the photograph of an identification card with a timeand date of the taking the photograph of the identification card;sending the photograph of the face and the photograph of theidentification card to a site; receiving the photograph of the face andthe photograph of the identification card; comparing the photograph ofthe face and the picture in the photograph of the identification card;determining if the photograph of the face and the picture are the same;determining if the GPS coordinates of the first location and the GPS ofthe second location are substantially the same; determining if the timeand date of the taking the photograph of face and the time and date ofthe taking the photograph of the identification card are within adefined time window; and generating an authorization key, if thephotograph of the face and the picture are the same, if the firstlocation and the GPS of the second location are substantially the same,and if the taking the photograph of face and the time and date of thetaking the photograph of the identification card are within the definedtime window.

In some embodiments, the authorization key is a token configured toallow a User to access secured websites. The method can include the stepof: collecting data comprising at least one of a name, an address, abirthdate, and a gender from the photograph of the identification cardand connecting the data to the authorization key. The method can be partof a mobile application, which improves security for a range ofinternet-related activities.

Additional methods for providing a secured system and various systemsfor providing online verification and security are described herein.Some embodiments of the methods and systems provide an “identificationcard” for the internet. Applications for such methods and systems caninclude, for example: dating sites, online employment applications,legal notary services, childcare services, online gambling, and securedsocial networking sites.

DRAWINGS

The present disclosure will become more fully understood from thedescription and the accompanying drawings, wherein:

FIG. 1 is a flowchart illustrating various elements for providing theonline verification methods and systems, in accordance with variousembodiments;

FIG. 2 is a flowchart illustrating an exemplary process flow ofverification between the various elements for providing the onlineverification methods and systems as illustrated in FIG. 1, in accordancewith various embodiments;

FIG. 3 is a flowchart illustrating an exemplary process flow ofsecondary verification between the various elements for providing theonline verification methods and systems as illustrated in FIGS. 1 and 2,in accordance with various embodiments;

FIG. 4 is a flowchart illustrating an exemplary outline for creating aUser account, in accordance with various embodiments;

FIG. 5 is a flowchart illustrating an example of privacy setting for aUser account, in accordance with various embodiments;

FIG. 6 is a flowchart illustrating an exemplary User process flow ofverification and use, in accordance with various embodiments;

FIG. 7 is a flowchart illustrating an exemplary process flow forproviding the online verification methods and systems, in accordancewith various embodiments; and

FIG. 8 is a flowchart illustrating an exemplary process flow forproviding the online verification methods and systems, in accordancewith various embodiments.

The drawings described herein are for illustrative purposes only ofselected embodiments and not all possible implementations, and are notintended to limit the scope of any of the exemplary embodimentsdisclosed herein or any equivalents thereof. It is understood that thedrawings are not drawn to scale. For purposes of clarity, the samereference numbers will be used in the drawings to identify similarelements.

DESCRIPTION

The following description is merely exemplary in nature and is in no wayintended to limit the exemplary embodiments, their application, or uses.It should be understood that steps within a method may be executed indifferent order without altering the principles of the presentdisclosure. For example, various embodiments may be described herein interms of various functional components and processing steps. It shouldbe appreciated that such components and steps may be realized by anynumber of hardware components configured to perform the specifiedfunctions.

Various embodiments provide methods and systems for providing onlineverification and security. Some embodiments include methods forproviding a secured system. Various methods and systems, describedherein, can be a mobile application, which improves security throughouta whole range of internet-related activities.

In some embodiments, methods and systems, described herein, improvesecurity for online or internet-related activities in at least threeways. First, individual users are provided the means to prove theiridentity on the Internet through a proprietary process of IDverification in time, place, and device. Second, Internet providers areprovided the means to verify that their own users are using their realidentities, and that the person who currently is using their service isindeed that verified individual. Third, the public is provided the meansto ensure that they are not being misled, harassed, or threatened byanonymous or fraudulent Internet miscreants.

The methods and systems are designed to utilize an integratedcombination of just in time, just in place, and just on device actionsconnected to an image recognition process to reduce or remove the riskof a User utilizing fake or stolen credentials in order to get verified.

For example, a method of identification verification can includeaccessing the verification application on a mobile device and completinga registration process. The verification application can be interfacedwith a verification engine on webserver, which is communication with themobile device. In some cases, it may appear to the User that theverification application is doing an analysis to determine an outcome,but the analysis is actually being run by the verification engine.First, the User is instructed to take a picture or a short video ofhim/her with their mobile device (“User photo”). The User can be allowedto repeat this process until the User is satisfied with the image. TheUser is then given a limited number of minutes to take a photograph oftheir government identification card (“ID Card photo”), such as, forexample, a driver's license, a state ID card, a passport, a school ID,or any such identification device, which has a photograph of the User.

The verification application can capture the time, date, and GPScoordinates for the User photo and the ID Card Photo. In some aspects,the verification application can capture the meta-data from the User'smobile device. The verification application determines if the process oftaking the User photo and the ID Card photo are completed in the sametime, in the same place, and on the same device. If yes, the processcontinues. If no, the verification application notifies the User torepeat the process of taking the User photo and the ID Card photo.

The ID Card photo is processed. First, the User photo is compared to thephoto of the User in the ID Card photo using facial-recognition routinesto determine if the same person is on both photos. Second,identification information (“ID Info”), which is in text form in the IDCard photo, can be captured using an OCR routine. The ID Info caninclude name, address, birthdate, gender, driver's license number,and/or any other information on the government identification card. Insome applications, the ID Info can be read from a barcode on ID Card. Ifthe barcode is located on a back side of the ID Card, a second ID Cardphoto of the back of the ID Card may be required. The ID Info can becompared to the information provide in the registration process.

In addition, the verification application can verify that the ID Info isvalid via a comparison with the appropriate governmental records. Forcertain applications, the verification application can verify that theID Info is not on the National Sexual Predator List or similar sexualpredator database.

If the application confirms that the process of taking the User photoand the ID Card photo are completed in the same time, in the same place,and on the same device, and if the facial-recognition routines determinethat the same person is on the User photo and the ID Card photo, and ifthe ID Info is valid via a comparison with the appropriate governmentalrecords, then verification application will determine the User is“Verified” (or “Veried™”). Once the verification application hasVerified the User, the application issued an authorization key to theUser. In some applications, the authorization key is a token configuredto allow the User to access secured websites. For example, the token canbe provided to various online providers.

In some applications, one or more addition requirements can be used todetermine if the User is Verified. For example, an additionalrequirement can be if the ID Info is not on the National Sexual PredatorList or similar sexual predator database. For example, an additionalrequirement can be a certain age limit (as compared to ID Info), whichmay be required for any internet activity directed to tobacco, alcoholicbeverages, or online gambling. An additional requirement can be entry ofa state or board professional license, which can be determined if thelicense is valid via a comparison with the appropriate governmental orprofessional organization records. Such a professional license caninclude but is not limited to: law license, boards for doctors, boardsfor dentists, contractor license, notary certification, beauticianlicense, bonding, chauffer license, and the like.

All of the requirements to be Verified, as well as, the ID Info, theUser photo, the ID Card photo, and the meta-data are connected to a UserProfile, which can be connected to or part of the token. Otherinformation that can be connected to the User Profile can include, butare not limited to: criminal background checks, state or boardprofessional licenses, product usage, internet usage, survey results,social networking pictures of User (which can be used for furtherverification), sexual and/or dating preferences, data from internetproviders, and the like. In some applications, the User can connectinformation to the User Profile.

In some embodiments, a User can control the privacy setting of the UserProfile and the web provider (partner) can control settings for therequired information needed from the User. In some applications, theUser can set the privacy setting to anonymous, however, the web providerhas all of the required information that is necessary to be Verified. Ifthe anonymous User becomes a web bully or a predator, the web providercan remove the Verification from the User. In addition, the web providerhas all the information to identify such a rogue User, which can beturned over to the authorities if any cybercrimes have been committed.In some applications, the User can set the privacy setting to allowvarious social networking information or business contact information tobe connected to the token. For example, the User can connect Facebookpages, Twitter accounts, blog pages, websites, and the like to thetoken, all of which can be viewed by others (either publicly or limitedto certain web providers (partners)) based on the privacy setting chosenby the User.

In some embodiments, the data can be collected and connected to thetoken every time the token is used or logged in. For example, such datacan include, but is not limited to: when was it used (time/date), deviceit was used from, device ID it was used from, website/service where itwas used, product that it was used for, number of times token waschecked/verified by outside users, websites on which those verificationstook place, products for which those verifications took place, devicefrom which those verifications took place, and/or demographicinformation on Users that verified an ID.

From time to time, the verification application can be configured torecheck any of the requirements. For example, once a year, theverification application can be configured to recheck the ID Infoagainst the National Sexual Predator List or similar sexual predatordatabase.

In some embodiments, secondary verification data can be collected andconnected to the token. The verification application can prompt the Userto read a couple of sentences into their mobile device, which isrecorded by the verification application. This recording can be storedfor use in voice-recognition applications. For example, the verificationapplication may ask the User to apply a thumbprint and/or fingerprint toan interface on their mobile device. The thumbprint and/or fingerprintis recorded as a secondary verification data and stored for use infingerprint-recognition applications. In other example, the verificationapplication may ask the User to an image of the User's retina. Theretina image is recorded as a secondary verification data and stored foruse in image-recognition applications. From time to time the User may beasked to renew their Verification status by completing the above processagain.

In some embodiments the verification application may request of prooffrom the User that the person using the device is actually the User.This request may be generated on a prescribed time period or randomly.This request may be generated when the application identifies that theGPS of the device is outside a boundary. The boundary can be changed bythe User. For example, if User resides in Texas and the device is beingused in Nigeria, a request of proof from the User is generated. Inanother example, if User's device is being used in domestically but in adifferent time zone, a request of proof from the User is generated.

For example, the form of proof can be a request for the User to take anew User photo, which is submitted and compared, using thefacial-recognition routine, to User photo(s) and ID Card photo(s) in theUser Profile. For example, the form of proof can be a request for theUser to read a few words aloud into the verification application, whichis submitted and compared, using a voice-recognition routine, topreviously recorded User's voice in the User Profile. For example, theform of proof can be a request for the User to apply a fingerprintand/or a thumbprint or both to an interface on their mobile device,which is submitted and compared, using a fingerprint-recognition routineto the fingerprint and/or thumbprint of User in the User Profile. Forexample, the form of proof can be a request for the User to take animage of the eye retina, which is submitted and compared to the image ofthe eye retina of the User in the User Profile.

Partners can connect with verification system (“Verie”) through a secureAPI, which provides the partners with the means to deliver verificationtechnology to their end users' smartphones. After verifying a User'sidentity, the verification system can quickly re-verify a user anytime,anyplace.

Some embodiments provide a verification engine, which is an identityverification technology solution. By combining a proprietarysmartphone-based identification application with an enterprise API, theverification engine allow partners to verify that an online individualis truly who they say they are. The verification engine can confirm thata person's online identity is real, and that it belongs to the personwho is claiming it. The verification engine can identify the physicallocation of the individual. The verification engine establishes anidentification, which cannot be duplicated, because it is uniquely tiedto the individual's smartphone.

In some embodiments, a User creates a User Profile by submitting afive-second video clip of their face and a snapshot of the front andback of their driver's license through a verification app, which hasbeen loaded the User's smartphone. The verification app sends the videoand the images to a verification engine, which matches the facial videowith the ID photo and determines if the ID Card is legitimate.Voice-prints are then recorded then sent to the verification engine tomake future re-verifications quick and unobtrusive. Once the User's IDis recorded, face-matched, and registered, the User's smartphone becomesthe User's online proof of identity.

In some embodiments, a method for providing a secured system can includethe steps of: taking a photograph of face at first location with adevice comprising a clock and a GPS; tagging the photograph of face withGPS coordinates of the first location; tagging the photograph of facewith a time and date of the taking the photograph of face; taking aphotograph of an identification card comprising a picture at a secondlocation; tagging the photograph of an identification card with GPS ofthe second location; tagging the photograph of an identification cardwith a time and date of the taking the photograph of the identificationcard; sending the photograph of the face and the photograph of theidentification card to a site; receiving the photograph of the face andthe photograph of the identification card; comparing the photograph ofthe face and the picture in the photograph of the identification card;determining if the photograph of the face and the picture are the same;determining if the GPS coordinates of the first location and the GPS ofthe second location are substantially the same; determining if the timeand date of the taking the photograph of face and the time and date ofthe taking the photograph of the identification card are within adefined time window; and generating an authorization key, if thephotograph of the face and the picture are the same, if the firstlocation and the GPS of the second location are substantially the same,and if the taking the photograph of face and the time and date of thetaking the photograph of the identification card are within the definedtime window.

In some embodiments, the authorization key is a token configured toallow a User to access secured web sites. The tags on the User photoand/or the ID Card photo can include the unique device ID, a devicetype, and in some applications, the operating software (OS) on thedevice.

The method can include the step of: collecting data comprising at leastone of a name, an address, a birthdate, and a gender from the photographof the identification card and connecting the data to the authorizationkey. Further, the data can also include: ID type, ID number, issue date,expiration date, and identifying information (such as, height, weight,eye color, hair color, organ donor, any other available identifyinginformation).

The method can include the step of: comparing the data to a database anddetermining if the database identifies a defined null value. Forexample, the data base comprises a criminal history and the defined nullvalue is a sexual predator conviction. The method can include automaticcross checking of Users against databases (such as, sex offenderregistry, criminal background, credit check, etc.). The method caninclude the step of: denying the authorization key if the databaseidentifies the defined null value. The method can include the step of:comprising denying the authorization key if an age as calculated by thebirthdate is below a defined age threshold. For example, the defined agethreshold is 21 years old (applications such as alcoholic beverages).For example, the defined age threshold is 18 years old (applicationssuch as online gambling and tobacco). For example, the defined agethreshold is 13 years old (applications such as general use of theinternet).

In some embodiments, the GPS coordinates can include the angle the photowas taken using the gyroscope in the device. In some aspects of theseembodiments, a first photo of the ID Card is taken at a first angle anda second photo of the ID Card is taken at a second angle. The firstangle and the second angle can be recorded by the device and tagged tothe photos. A holograph or an embossed symbol may be identified on theID Card by using the angle of the first photo and the angle of thesecond photo.

In some embodiments, the User photo and the ID Card photo must be takenwithin a defined time period. For example, the User photo and the IDCard must be taken within a one minute time period. This time period canbe varied depending on the application. The GPS coordinates tagged tothe User photo and tagged to the ID Card photo must be within a defineddistance. For example, the GPS coordinates tagged to the User photo andtagged to the ID Card photo must be within 20 feet. In another example,the GPS coordinates tagged to the User photo and tagged to the ID Cardphoto must be within 3 feet. The defined distance of the GPS coordinatescan be varied depending on the application; however, this distance mustbe greater than the margin of error of the GPS based on the capabilitiesof the device and the accuracy of the satellites used by the GPS.

Some embodiments provide a method for providing a secured system. Themethod can include the steps of: generating an image of a face of a userat first location with a device comprising a clock and a GPS; taggingthe image with GPS coordinates of the first location; tagging the imagewith a time and a date of the generating of the image; generating animage of an identification card comprising a picture of the user at asecond location; tagging the image of the identification card with GPScoordinates of the second location; and tagging the image of anidentification card with a time and date of the generating of the imageof the identification card.

The method can further include the steps of: comparing the image of theface and the image of the picture of the user; determining thelikelihood that the image of the face and the image of the picture ofthe user are substantially the same; determining if the GPS coordinatesof the first location and the GPS of the second location aresubstantially the same; determining if the time and date of thegenerating the image of face and the time and date of the generating theimage of the identification card are within a defined time window. Oneor more of these steps can be carried out by a verification engine on aweb server.

The method can further include the step of: generating an authorizationkey, if the image of the face and the image of the picture of the userare substantially the same, if the first location and the GPS of thesecond location are substantially the same, and if the time and date ofthe generating the image of face and the time and date of the generatingthe image of the identification card are within the defined time window.

In some aspects, the authorization key is a token configured to allow auser to access a secured website. In some aspects, the method caninclude the step of collecting data comprising at least one of a name,an address, a birthdate, and a gender from the photograph of theidentification card and connecting the data to a user profile. The datacan include at least one of an identification card type, anidentification card number, an identification card issue date, anidentification card expiration date, and an identification card issuingagency. The data can include at least one of a height, a weight, an eyecolor, a hair color, an organ donor status, and a bar code.

The method can include the step of denying the authorization key if anage as calculated by the birthdate is below a defined age threshold. Themethod can include the steps of: comparing the data to a database;determining if the database identifies a defined null value; andpreventing the generating the authorization key if the null value isidentified. The database can include a sex offender registry and thedefined null value is a sexual predator. The database can include acriminal history and the defined null value is a criminal conviction.The database can include a credit history and the defined null value isa credit score below a defined value. The method can include the step ofdenying the authorization key if an age as calculated by the birthdateis below a defined age threshold.

The method can include the steps of: scanning the image of theidentification card for a hologram; comparing the hologram to a standardfrom a database; determining if the identification card is fraudulent;and preventing the generating of the authorization key if theidentification card is fraudulent. The method can include the step ofinitiating an app on the device, the app configured to carry out all ofthe steps of the method. The method can include the step of retrievingdevice identification data from the device.

The method can include the steps of tagging the image with the deviceidentification data of the device generating the image of the face; andtagging the image of the identification card with the deviceidentification data of the device generating the image of theidentification card. The method can include the step of determining ifthe device identification data of the device generating the image offace and the device identification data of the device generating theimage of the identification card are the same.

The method can include the step of generating the authorization key, ifthe image of the face and the image of the picture of the user aresubstantially the same, if the first location and the GPS of the secondlocation are substantially the same, if the time and date of thegenerating the image of face and the time and date of the generating theimage of the identification card are within the defined time window; andif the device identification data of the device generating the image offace and the device identification data of the device generating theimage of the identification card are the same.

The method can include the steps of receiving and storing an initialsecondary identifier after the generating the authorization key;requesting user to input a secondary identifier at a later time;receiving the secondary identifier from the user; comparing thesecondary identifier to the initial secondary identifier; determining ifthe secondary identifier and the initial secondary identifier aresubstantially the same; and renew the authorization key if the secondaryidentifier and the initial secondary identifier are substantially thesame.

The secondary identifier can be one of: a voice pattern generated by theuser and captured by a microphone on the device; an image of a retina ofa user's eye captured by the device; at least one fingerprint of theuser captured by the device; a palm scan of the user captured by thedevice; a photo of the user captured by the device; a RFID tag tetheredto the device; and a password.

Some embodiments provide a system for secured transactions over anetwork. The system can include an app, which is downloadable to adevice, a verification engine on a server at the location on thenetwork, and a verification token configured to allow the user access toat least one restricted website.

The device can be a smart phone or tablet, however, the device has atleast a camera, a GPS locator, a network interface, and a userinterface.

In some configurations, the app includes: a process to imitate a user totake and capture a picture of a user's face with the camera; a processto capture a first set of GPS coordinates, a first time, and a date ofthe picture of the user's face; a process to initiate the user to takeand capture a picture of an identification card with the camera; aprocess to capture a second set of GPS coordinates, a second time, and adate of the picture of the identification card; a process to captureidentification data of the device; a process to send data comprising atleast one of the picture of the user's face, the picture of theidentification card, the first set of GPS coordinates, the second set ofGPS coordinates, the time and date of the picture of the user's face,the time and date of the picture of the identification card, and theidentification data to a location on the network; and a process toreceive and communicate information.

In some configurations, the verification engine includes: an inputconfigured to receive the data from the app; an image comparisonalgorithm configured to compare the picture of the user's face, thepicture of the identification card, then determine the likelihood thatthe user and a person in the picture of the identification card aresubstantially the same; a location comparison algorithm configured todetermine if the first set of GPS coordinates and the second set of GPScoordinates are substantially the same; and a time comparison algorithmconfigured to determine if the time and date of the picture of theuser's face, the time and date of the picture of the identification cardare substantially the same.

In some configurations, the is configured to be send to the app if theuser and a person in the picture of the identification card aresubstantially the same, if the first set of GPS coordinates and thesecond set of GPS coordinates are substantially the same, and if thetime and date of the picture of the user's face, the time and date ofthe picture of the identification card are substantially the same.

In some aspects, the system includes a not verified message configuredto be sent to the app if at least one of an outcome of the imagecomparison algorithm is negative, or if an outcome of the locationcomparison algorithm is negative, or if an outcome of the timecomparison is negative.

The system can include a secondary verification system. The secondaryverification system can be configured to: receive and store an initialsecondary identifier at a first time; receive a second secondaryidentifier at a second time; compare the second secondary identifier tothe initial secondary identifier; determine if the second secondaryidentifier and the initial secondary identifier are substantially thesame; and renew the verification token if the second secondaryidentifier and the initial secondary identifier are substantially thesame.

The secondary identifier can be an image of a retina of a user's eyecaptured by the camera. The secondary identifier can be at least onefingerprint of the user captured by the device. The secondary identifiercan be a voice pattern generated by the user and captured by amicrophone on the device.

The system can include an interface between the verification engine anda third-party server. The interface can be configured to sendverification parameters from the third-party server and to receiveresults from verification engine. The system can include an interfacebetween the verification token and a third-party server, wherein theinterface is configured to notify the third-party server that theverification token has been sent to the user.

The system can include a user profile comprising a user name and atleast one piece of data from the identification card. In someconfigurations, the at least one piece of data comprises at least one ofa legal name, an address, a birthdate, a gender and a picture of theuser. In some configurations, the verification engine is configured tocollect text from the identification card, convert the text into the atleast one piece of data and enter the at least one piece of data intothe user profile. In some configurations, the user profile comprises theidentification data from the device. In some configurations, the userprofile is configured to allow the user to add personal information. Insome configurations, the personal information comprises at least one ofan email address, a social media page, a credit card, a marital status,a military status, a school, and a student number. The system caninclude a privacy setting configurable by the user and controlling whichitems in the user profile are viewable by other users.

Now with reference to FIG. 1, a flowchart illustrates various elementsfor providing the online verification methods and systems. The User 101operates the device 103 via user interface 102. The device 103 can beany device with a user interface 102, an image capture mechanism, andweb capabilities. An image capture mechanism can be a digital device, amechanical device, or a combination of both. The web capabilities can bea Wi-Fi interface, a Bluetooth interface, a mobile service interface, orany other such system or device, now known or developed in the future.Examples of the device 103 can include smartphones, tablets, and othersuch devices. For example, the device 103 can be an iPhone, an iPad, anapple watch, and other such devices. Examples of the device 103 caninclude phones and tablets, which operate on android operating systems.Other examples of the device 103 can include phones and tablet, whichoperate on Microsoft operating systems. In some aspects, the device 103can be a laptop computer with wireless network capabilities and an imagecapture device. The device 103 can interface with the server 105 via anetwork, such as a cloud. The device 103 can have an verification app104 (sometimes referred to as an “app” herein) installed which cancommunicate with the User 101 via the user interface 102 and communicatewith the server 105 via a network connection. The server 105 interfaceswith partners 107 via link 106, which can be a third-party contentprovider or third-party web service. A verified access key 111, whichcan be a token, allows the User 101 to use a service or access a website of one of the partners 107.

In FIG. 2, a flowchart illustrates details of an exemplary process flowof verification between the various elements for providing the onlineverification methods and systems as illustrated in FIG. 1. Asillustrated in FIG. 2, User 101 can use the device 103 to generate animage of an identification card (“ID”), which is stored on the device103 by verification app 104. A verification engine on the server 105isolates the User's image from the ID (“ID photo”) and isolates personaldata from the text and/or bar code on the ID.

The User 101 takes one or more pictures or a video of self with thedevice 103 (“User photo”). In some configurations, the verification app104 can be used to confirm that the User 101 in the picture or video isa live person. In some configurations, the verification engine on theserver 105 can be used to confirm that the User 101 in the picture orvideo is a live person.

The User 101 provides a self-image by using the device 103 to take oneor more pictures or video of the User's face. One or more stills fromthe video can be compared to confirm that the self-image is that of alive person. In the alternative, two or more pictures compared toconfirm that the self-image is that of a live person. These comparisons,using either photos, stills from a video, or a combination of both, canbe a “liveness test”. In some embodiments, a “liveness test” can beperformed to confirm that the self-image is of a living person. Forexample, a short video make be taken and the User 101 is asked to openand close eyes during the video. In an example, the video can be scannedfor still images of open eyes and of closed eyes. If both types ofimages exist, then the self-image passes the “liveness test” and theuser considered a living person. Another example can include a firstphoto with eyes open and a second photo with eyes close. If both ofthese photos are sent then an algorithm can be used to confirm that theUser's image is that of a living person. For these examples, a smile/nosmile could be substituted for the eyes opened/closed. For theseexamples, a hand on face/no hand on face could be substituted for theeyes opened/closed. As is obvious to one skilled in the art, any numberof different positions, gestures, expressions during the self-imagephotos or video could be used. In another example, a short video make betaken while moving the camera around the User's face, for example movingthe camera for ear to ear in a motion that is somewhat perpendicular tothe face. In an example, the video can be scanned for different views ofthe face, which can used to determine that the User face is a 3D object,which passes the test and the User 101 is a living person (not a photoof a 2D picture). Another example can include a first photo of the frontof the User's face and a second photo of a side angle of the User'sface. If both of these photos are sent then an algorithm can be used toconfirm that the User's self-image is that of a living person. In suchan example, the angle the photos were taken can be determined by using agyroscope in the device 103. Of course these and other examples can becombined to send both 3D views of the User's face and differentgestures/expressions on the User's face to an algorithm to confirm thatthe User's self-image is that of a living person.

The verification engine compares the User photo with the ID photo thenestablishes the likelihood that the User photo and the ID photo areimages of the same person. The User 101 enters personal data into theapp 104 and the verification engine determines if the entered personaldata matches the personal data from the ID. In addition, the validity ofthe ID is determined by a comparison with an appropriate database. Thepersonal data and images are stored on the server 105. Theidentification data from the device 103 (“device ID”) can be retrievedby the app and stored on the server 105. A User Profile can include theUser photo, the ID photo, the personal information, and the device ID.If the entered personal information and the personal information fromthe ID matches and the User photo and the ID photo are likely the sameperson, and the ID is valid, then the server 105 sends a token to one ormore of the partner 107, which establishes that the User 101 isverified. The token can be used as or used to establish a verifiedaccess key 111, which allows the User 101 to interface with the partner107. The token can be sent to the verification app 104 on the device103, which allows the User 101 to access partner 107 with device. Iftoken is sent to device 103, the User 101 may have access to a group ofpartners who accept a User 101 who has been verified.

Some optional aspects are also illustrated on FIG. 2. In an option, thepartner 107 can request and receive additional information from User101, which is used to determine if the User 101 can be verified. If theUser 101 passes the criteria set for the additional information, thenthe server 105 sends a token to one or more of the partner 107, whichestablishes that the User 101 is verified. In an option, the server 105can cross-check the User 101 against a third-party database, such as,for example, a sexual predator database, criminal history database,credit history, or the like. If the User 101 passes the criteria set forthe third-party database, then the server 105 sends a token to one ormore of the partner 107, which establishes that the User 101 isverified.

In still another option, the partner 107 can require real-timeverification from the User 101. The partner 107 can send a request tothe User 101 to provide a new User photo before access can be permitted.The User 101 takes a new User photo, as described herein, which sent tothe server 105 and determined if the new User photo is the same person,who was originally verified. If the new User photo confirms that theUser 101 is the same person, who was originally verified, then serverrenews or sends a new token to partner 107, which grants access to User101. Other examples of real-time verification are illustrated in FIG. 3.

In another option, the User 101 can set the privacy of the User Profile,which has been entered into the server 105. The privacy setting of theUser Profile can limit the information/data available to the partners107. The privacy setting of the User profile can limit theinformation/data available to other users or the public. Other examplesof privacy settings are illustrated in FIG. 5.

In FIG. 3, a flowchart illustrates details of an exemplary process flowof secondary verification between the various elements for providing theonline verification methods and systems as illustrated in FIGS. 1 and 2.For example, the verification app 104 can be configured to receive andstore an initial secondary identifier on the server 105 after the tokenis created. The partner 107 can request User 101 for real-timeverification, which requires the User 101 to input a secondaryidentifier, which is sent to the server 105. The server 105 compares thesecondary identifier to the initial secondary identifier and determinesif the secondary identifier and the initial secondary identifier aresubstantially the same. The server 105 sends/renews the token to thepartner 107, if the secondary identifier and the initial secondaryidentifier are substantially the same. Examples of the secondaryidentifier include, but are not limited to: a voice pattern generated bythe User 101 and captured by a microphone on the device 103; an image ofa retina of a User's eye captured by the device 103; at least onefingerprint of the User 101 captured by the device 103; a palm scan ofthe User 101 captured by the device 103; a photo of the User captured bythe device; a RFID tag tethered to the device 103; and a password. Thesecondary identifier can be added to the User Profile.

As illustrated in FIG. 3, the User 101can enter at least one secondaryidentifier, which can be any of or all of a voice sample, an image offingerprint(s), and an image of eye retina, into the device 103. Theverification 104 sends the secondary identifier(s) to User Profile,which is stored on the server 105. When the partner 107 sends a requestto the User 101 for secondary verification, the User 101 is required toenter the required secondary identifier, such as, the voice sample, theimage of fingerprint(s), and/or the image of eye retina, into the device103, within a limited time window. For example, within 1 minute of thereceipt of the request. If the required secondary identifier is notentered within the limited time window, access to the partner 107 isdenied. The required secondary identifier, as entered by the User 101,is sent to the server 105 to be compared to the secondary identifier,which is stored as part of the User Profile. If the User input matchesthe secondary identifier in the User Profile, a token is granted orrenewed. However, the partner 107 can limit access within certaingeographical boundaries. If the device 103 is outside of the boundaries,then access is denied. However, if the device 103 is outside of theboundaries the partner 107 may require real-time verification todetermine if the verified User 101 is attempting to access partner 107.In some configurations, the partner 107 can deny access if the device103 is unable to provide a location or provide device ID.

FIG. 4 illustrates a flowchart, which outlines an exemplary outline forcreating a User account. In some embodiments, the User 101 downloads theverification app 104 onto the device 103. The verification app 104 canrequire the User 101 to enter a user name and a password to begin theprocess to establish an account. The verification app 104 is configuredto collect all images and data through the device 103. For example, theverification app 104 can control the camera of the device 103 to collectimages. For example, the verification app 104 can provide the User 101pages with areas to fill in required information/data. The verificationapp 104 can be a web based application, which is connected toverification engine residing on a server 105 in a cloud that is incommunication with the web.

As illustrated in FIG. 4, the device 103 is configured to collect allimages and data through the verification app 104. The User 101 enters anemail address and a password in verification app 104. The User 101generates a digital image of ID with the device 103. The app 104 sendsthe digital image of ID to server 105, which is configured to isolatethe ID photo on the ID. In addition, the server 105 is configured toisolate text, data, and/or a bar code on the ID and parse theinformation into specific data fields. For example, the address iscollected from the text on the ID or from a bar code on the ID and thenthis address is entered into the data field for addresses. The User 101is then given a limited amount of time, for example 1 minute, to reviewand confirm the data fields. If the limited amount of time expires, thenthe User 101 is directed back to the page that generates a digital imageof ID. If a data field is incorrect, the User 101 may be allowed to editthe data field.

If the data fields are confirmed, the User 101 is then required to takea self-picture/video (“User photo”) with the device 103. If the User 101has elected to enter a self-video, still images from the video areisolated. The system can use a “liveness test” to confirm the User photois of a live person, who is the User 101. Methods to confirm that anentered image is of a real and/or a live individual are describedherein. Any such tests, methods, comparisons, and/or algorithms can beused here. The ID photo and User photo are compared, using for example abiometric routine, and the data is used to calculate the statisticallikelihood that the ID photo and the User photo are the same person. Ifthe statistical likelihood is above (greater than) a defined threshold,then there is a Match. For example, the defined threshold can be atleast 85% likelihood. In some applications, the defined threshold may berequired to be greater than 95%. If the statistical likelihood is below(less than) a defined threshold, then there is a Fail and the User 101is directed back to the page that generates a digital image of ID.

If there is a Match, the GPS location of the ID Card photo and the GPSlocation of User photo are compared. If the two GPS locations aresubstantially the same, then there is a second Match. If the two GPSlocations are different, then there is a Fail and the User 101 isdirected back to the page that generates a digital image of ID.

After the second Match, the User 101 is requested to enter a set ofrequired personal information/data. In the example of FIG. 4, the set ofrequired personal information/data include entering: the last fourdigits of ID, an email address, the user name and password, and thephone number of the device 103. However, the set of required personalinformation/data can be any set of such information/data as provided byany one of the partners 107. The verification app 104 collects thedevice ID and GPS location. In the example of FIG. 4, the device IDincludes the GPS location, the device type, the operating system, thedevice phone number, and the IMEI number. The User account is thencreated. The User account then sends out a confirmation email to theUser. In some configurations, the User 101 is taken to a dashboard tofurther set up and/or use the account (which is an optional step). Afterverification, the account is activated.

Moving to FIG. 5, a flowchart illustrates various privacy settings forthe User Profile. The User Profile includes a user name and at least onepiece of data from ID, for example, the at least one piece of datacomprises at least one of a legal name, an address, a birthdate, agender, a User photo, and an ID photo. The User Profile can include thedevice ID. In some configurations, the User 101 is required or allowedto add personal information to the User Profile. For example, thepersonal information can be, but not limited to: an email address, asocial media page, a credit card, a marital status, a military status, aschool, and a student number.

As illustrated in FIG. 5, the User 101 can establish the privacy settingto a public profile, which can be the default settings, as well as theprivacy setting to one or more specific partners 107. Of course any ofthe items in the User Profile can be limited by privacy setting,however, one or more of the items in the User Profile maybe required bythe partners 107, which cannot be controlled through the privacysettings. In the example in FIG. 5, the User 101 can control the privacysetting of an exemplary set of items comprising name, date of birth,address, photo, social security number, gender, and criminal record. Inthis example, the User 101 can control which of these items are viewableby the public or other users. In one example, the User 101 could blockdate of birth in the public profile but the specific partner 107requires the date of birth, therefore the User 101 cannot block thisitem from the specific partner 107. In some applications, such as, adating site, the partner 107 may require that the User photo is notblocked by privacy settings. In some configurations, the privacysettings can allow a User 101 to enter social site, which is hosted by apartner 107, anonymously. In some configurations, the privacy settingsallow the User 101 to not be tracked when using a partner 107 site orwhen ordering merchandise or services from a partner 107.

In some applications, the User 101 can set the privacy setting to allowvarious social networking information or business contact information tobe connected to the token. For example, the User 101 can connectFacebook pages, Twitter accounts, blog pages, websites, and the like tothe token, all of which can be viewed by others (either publicly orlimited to certain partners 107) based on the privacy setting chosen bythe User 101.

FIG. 6 provides a flowchart illustrating an exemplary User process flowof verification and use. The verification app can offer the User 101 avariety of options. For example, the User 101 can view her User Profile.The User 101 can change/control the privacy setting of the User Profile,which is stored on the server 105. The User 101 can change/updatepersonal information/data, which is stored on the server 105. The User101 can update an expired ID Card, which is stored on the server 105.The User 101 be in contact with customer serve through the verificationapp. The User 101 can update User images, which may need to be verifiedbefore being stored on the server 105. The User 101 can manage thepartner sites 107 that the User 101 has a token to access. The User 101can update the list of partner sites 107 by deleting a site and/or byapplying for access to a different site. A partner 107 can requestupdated User 101 verification status from the server 105. A partner 107can request real-time verification from the User 101. The server 105 canprovide updates to one or more partners 107, after User 101 has madechanges to the User Profile

Now turning to FIG. 7, a flow chart illustrates a verification methodand system. The User 101, by employing the user interface 102, uses theverification app 104, which is installed on the device 103, to performthe various functions. The User 101 uses device 103 to capture aself-image. The self-image can be photo or s series of photos. Theself-image can be a short video, from which a set of still images can beisolated. In some embodiments, a “liveness test” can be performed toconfirm that the self-image is of a living person, as has been discussedherein. The captured self-image(s) or video is sent to the server 105for image enhancement and a determination if a face was detected in theself-image(s). The image enhancement can include enhancing stills from aself-image video. The User 101 uses device 103 to capture an image of anID Card. The image of the ID Card is sent to the server 105 for imageenhancement. The image enhancement can include isolating a photo fromthe ID Card and a determination if a face was detected from the photo.If a face is detected in the self-image and the ID image, then theself-image and the ID image are compared. An algorithm can be used tostatistically determine if the self-image and the ID image are a match.If yes, these images are a match, then the first prong of verificationhas been passed.

The User 101 uses device 103 to capture the bar code from the back ofthe ID Card. The barcode image is sent to the server 105 and the datafrom the barcode is parsed and entered into data fields. A determinationif someone else has the same ID Card using the data from the barcode. Ifno, then the ID Card is checked for validity. For example, the ID Cardis check for expiration. If no, the ID Card is not expired, the parsedID number/data from the barcode is compared to the ID number/datacaptured using OCR from the front of the ID Card. If yes, the ID numberfrom the barcode and the ID number from the front of the ID Card are thesame, then the second prong of verification has been passed.

The app 104 captures the UDID from the device 103 and sends the UDID tothe server 105. A determination if another device has the same UDID isqueried. If no, no other device has the same UDID, and the third prongof verification has been passed.

The app 104 captures the GPS coordinates from the self-image and the GPScoordinates of the image of the front of the ID Card then sends the twosets of the GPS coordinates to the server 105. If the two sets of GPScoordinates are substantially the same, then the fourth prong of theverification has been passed. In some embodiments, the app 104 capturesthe GPS coordinates from the self-image, the GPS coordinates of theimage of the front of the ID Card, and the GPS coordinates of the imageof the barcode, then sends all three sets of the GPS coordinates to theserver 105. If all three sets of GPS coordinates are substantially thesame, then the fourth prong of the verification has been passed.

The User 101 enters an email address and a password into the app 104 onthe device 103. The email address is sent to the server 105 and checkedto determine if another person has the same email address. If no, thenthe fifth prong of the verification has been passed.

If all five prongs of the verification have been passed, then the User101 has been verified. Once verified, the User can have a token (oraccess key) added to the device 103, which allows the User 101 access tovarious partners 107, as discussed herein. Once verified the server 105can send a partner 107 a token with allows User to access that partner'ssite and/or services. Secondary verification can be used to confirm Useris accessing a partner 107 with device 103, which have been verified.

Additional prongs, which are similar to the email verification, can beincluded in a verification process. For example, the User may beprompted by the app 104 to enter a SSN. The SSN, which was entered, isforwarded to the server 105 can checked against a database to determineif another person is using the same SSN. If yes, then this prong of theverification is not passed and the User 101 cannot be verified.Similarly, the User may be prompted to enter credit card information,which is reviewed in the same way. In another example, the User may beprompted to enter his/her zip code of residence, which can be runagainst a database of mailing addresses. As obvious to one skilled inthe art, any combination of personal data can be used in an additionalprong for verification. Additional tests or prongs for verification canbe added to any of the embodiments described herein and variationsthereof.

All prongs for verification must be passed for a User 101 to beverified. In the example illustrated in FIG. 7, five prongs forverification must be passed for a User to be verified. If a User doesnot pass one of the prongs for verification, a manual review of theUser's data can be commenced to determine if the User is the personclaimed to be. This manual review can use the standards for a notarypublic to verify the User. In some configurations, the manual review canbe initiated by the User 101. In some configuration, the manual reviewcan be automatically initiated by the system. In an example of themanual review, a User 101 enters his/her SSN and it is determined thatsomeone else is also using this SSN. The manual review can useadditional information connected to the SSN in the database to overridethe SSN failure and verify the User 101. The manual review can useadditional information for other sources to determine the identity ofthe User 101 and override the SSN failure then verify the User 101.Variations of the manual review can be added to any of the embodimentsdescribed herein and variations thereof.

With reference to FIG. 8, a flow chart illustrates a verification methodand system. The User 101, by employing the user interface 102, uses theverification app 104, which is installed on the device 103, to performthe various functions. The User 101 uses device 103 to capture aself-image. The self-image can be photo or s series of photos. Theself-image can be a short video, from which a set of still images can beisolated. In some embodiments, a “liveness test” can be performed toconfirm that the self-image is of a living person, as has been discussedherein. The captured self-image(s) or video is sent to the server 105for image enhancement and a determination if a face was detected in theself-image(s). The image enhancement can include enhancing stills from aself-image video.

The User 101 uses device 103 to capture an image of an ID Card. Theimage of the ID Card is sent to the server 105 for image enhancement.The image enhancement can include isolating a photo from the ID Card anda determination if a face was detected from the photo. If a face isdetected in the self-image and the ID image, then the self-image and theID image are compared. An algorithm can be used to statisticallydetermine if the self-image and the ID image are a match. If yes, theseimages are a match, then the first prong of verification has beenpassed.

The app 104 captures the UDID from the device 103 and sends the UDID tothe server 105. A determination if another device has the same UDID isqueried. If no, no other device has the same UDID, and the second prongof verification has been passed.

The app 104 captures the GPS coordinates from the self-image and the GPScoordinates of the image of the front of the ID Card then sends the twosets of the GPS coordinates to the server 105. If the two sets of GPScoordinates are substantially the same, then the third prong of theverification has been passed.

The app 104 captures the time and date from the self-image and the timeand date of the image of the front of the ID Card then sends the twosets of the time and date to the server 105. If the two sets of time anddate are substantially the same, then the fourth prong of theverification has been passed.

If all four prongs of the verification have been passed, then the User101 has been verified. Once verified, the User can have a token (oraccess key) added to the device 103, which allows the User 101 access tovarious partners 107, as discussed herein. Once verified the server 105can send a partner 107 a token with allows User to access that partner'ssite and/or services. Secondary verification can be used to confirm Useris accessing a partner 107 with device 103, which have been verified.

The methods and systems for verification can be employed in numerousdifferent applications. In one application, the methods and systems canbe employed in the financial services industry to secure transactions,for example, credit card transactions. In another application, themethods and systems can be employed for notary public services. Inanother application, the methods and systems can be employed in on-linetesting, which guarantees that the test taker is the person who supposedto take the test.

In another application, the methods and systems can be employed indating sites. In another application, the methods and systems can beemployed in online employment applications. In another application, themethods and systems can be employed in childcare services. In anotherapplication, the methods and systems can be employed in secured socialnetworking sites.

In some applications help ensure that the user is above a certain agelimit. For example, the methods and systems can be employed in on-linegambling, to ensure that the player is at least 18 years of age. Forexample, the methods and systems can be employed in on-line alcoholsales, such as, for example, interstate wine sales. In this example, themethods and systems can ensure the buyer of the alcohol is above 21years old. In another example, the methods and systems can be employedby partners providing content to mature audiences, such as, for example,pornographic content. In this example, the methods and systems canensure the buyer/user of the content is above 18 years old, or whateverage is statutorily appropriate.

Other applications of the methods and systems can include governmentagencies, for example, parolee surveillance, tracking sexual predators,prevent IRS fraud, prevent Medicare fraud, and many other examples. Anapplication of the methods and systems can include the use in on-lineC-to-Commerce sites and/or on-line B-to Business sites.

The methods and systems can provide a source of data collection for eachtime a token is used or a user logs in. Other examples of datacollection can include the tracking of: when was it used (time/date),device it was used from, device ID it was used from; website/servicewhere it was used; product that it was used for; number of times tokenwas checked/verified by outside users; sites on which thoseverifications took place; products for which those verifications tookplace; device from which those verifications took place; and demographicinformation on users that verified an ID.

As used herein, the phrase “at least one of A, B, and C” can beconstrued to mean a logical (A or B or C), using a non-exclusive logical“or,” however, can be contrasted to mean (A, B, and C), in addition, canbe construed to mean (A and B) or (A and C) or (B and C). As usedherein, the phrase “A, B and/or C” should be construed to mean (A, B,and C) or alternatively (A or B or C), using a non-exclusive logical“or.”

The present invention has been described above with reference to variousexemplary embodiments and examples, which are not intended to belimiting in describing the full scope of systems and methods of thisinvention. However, those skilled in the art will recognize thatequivalent changes, modifications and variations of the embodiments,materials, systems, and methods may be made within the scope of thepresent invention, with substantially similar results, and are intendedto be included within the scope of the present invention, as set forthin the following claims.

1. A method for providing a secured system, comprising; generating animage of a face of a user at first location with a device comprising aclock and a GPS; tagging the image with GPS coordinates of the firstlocation; tagging the image with a time and a date of the generating ofthe image; tagging the image with the device identification data of thedevice generating the image of the face generating a reference image ofthe user at a second location; tagging the reference image of the userwith GPS coordinates of the second location; tagging the reference imageof the user with a time and date of the generating of the referenceimage of the user; tagging the reference image of the user with thedevice identification data of the device generating the reference imageof the user; comparing the image of the face and the reference image ofthe user; determining the likelihood that the image of the face andreference image of the user are substantially the same; determining ifthe GPS coordinates of the first location and the GPS coordinates of thesecond location are substantially the same; determining if the time anddate of the generating the image of the face and the time and date ofthe generating the image of the identification card are within a definedtime window; determining if the device identification data of the devicegenerating the image of the face and the device identification data ofthe device generating the reference image of the user are the same; andgenerating an authorization key, if the image of the face and thereference image of the user are substantially the same, if the GPScoordinates of the first location and the GPS coordinates of the secondlocation are substantially the same, if the time and date of thegenerating the image of the face and the time and date of the generatingthe reference image of the user are within the defined time window, andif the device identification data of the device generating the image offace and the device identification data of the device generating thereference image of the user are the same.
 2. The method according toclaim 1, wherein the authorization key is a token configured to allowthe user to access a secured website.
 3. The method according to claim1, wherein an identification card comprises the reference image of theuser.
 4. The method according to claim 3, further comprising collectingdata comprising at least one of a name, an address, a birthdate, and agender from the image of the identification card and connecting the datato a user profile.
 5. The method according to claim 4, wherein the datafurther comprises at least one of an identification card type, anidentification card number, an identification card issue date, anidentification card expiration date, and an identification card issuingagency.
 6. The method according to claim 4, further comprising the stepsof: comparing the data to a database; determining if the databaseidentifies a defined null value; and preventing the generating theauthorization key if the null value is identified.
 7. The methodaccording to claim 6, wherein the database comprises a sex offenderregistry and the defined null value is a sexual predator.
 8. The methodaccording to claim 6, wherein the database comprises a criminal historyand the defined null value is a criminal conviction.
 9. The methodaccording to claim 6, wherein the database comprises a credit historyand the defined null value is a credit score below a defined value. 10.The method according to claim 6, comprising denying an authorization keyif an age as calculated by the birthdate is below a defined agethreshold.
 11. The method according to claim 3, further comprising thesteps of: scanning the image of the identification card for a hologram;comparing the hologram to a standard from a database; determining if theidentification card is fraudulent; and preventing the generating of theauthorization key if the identification card is fraudulent.
 12. Themethod according to claim 1, further comprising: receiving and storingan initial secondary identifier after the generating the authorizationkey; requesting user to input a secondary identifier at a later time;receiving the secondary identifier from the user; comparing thesecondary identifier to the initial secondary identifier; determining ifthe secondary identifier and the initial secondary identifier aresubstantially the same; and renew the authorization key if the secondaryidentifier and the initial secondary identifier are substantially thesame.
 13. The method according to claim 12, wherein the secondaryidentifier is one of: a voice pattern generated by the user and capturedby a microphone on the device; an image of a retina of a user's eyecaptured by the device; at least one fingerprint of the user captured bythe device; a palm scan of the user captured by the device; an image ofthe user captured by the device; a RFID tag tethered to the device; anda password.
 14. The method according to claim 12, wherein the initialsecondary identifier is the reference image of the user and secondaryidentifier is an image of the user's face captured by the device.
 15. Asystem for secured transactions over a network, the system comprising:an app downloadable to a device comprising a camera, a GPS locator, anetwork interface, and a user interface, the app comprises: a process toinitiate a user to take and capture a picture of a user's face with thecamera; a process to capture a first set of GPS coordinates, a firstdevice identification data, and a first time and date of the picture ofthe user's face; a process to initiate the user to take and capture apicture of an identification card with the camera; a process to capturea second set of GPS coordinates, a first second identification data, anda second time and date of the picture of the identification card; aprocess to send data comprising at least one of the picture of theuser's face, the picture of the identification card, the first set ofGPS coordinates, the second set of GPS coordinates, the first time anddate of the picture of the user's face, the second time and date of thepicture of the identification card, the first device identification dataand the second device identification data to a location on the network;and a process to receive and communicate information; a verificationengine on a server at the location on the network, the verificationengine comprising: an input configured to receive the data from the app;an image comparison algorithm configured to compare the picture of theuser's face, the picture of the identification card, then determine thelikelihood that the user and a person in the picture of theidentification card are substantially the same; a location comparisonalgorithm configured to determine if the first set of GPS coordinatesand the second set of GPS coordinates are substantially the same; and atime comparison algorithm configured to determine if the first time anddate of the picture of the user's face and the second time and date ofthe picture of the identification card are substantially the same; and adevice identification comparison algorithm configured to determine ifthe first device identification data and the second deviceidentification data are the same; a verification token configured toallow the user access to at least one restricted site, the verificationtoken configured to be sent to the app if the user and a person in thepicture of the identification card are substantially the same, if thefirst set of GPS coordinates and the second set of GPS coordinates aresubstantially the same, if the first time and date of the picture of theuser's face, the second time and date of the picture of theidentification card are substantially the same; and if the first deviceidentification data and the second device identification data are thesame.
 16. The system according to claim 15, further comprising asecondary verification system configured to: receive and store aninitial secondary identifier at a first time; receive a second secondaryidentifier at a second time; compare the second secondary identifier tothe initial secondary identifier; determine if the second secondaryidentifier and the initial secondary identifier are substantially thesame; and renew the verification token if the second secondaryidentifier and the initial secondary identifier are substantially thesame.
 17. The system according to claim 16, wherein the secondaryidentifier is one of: a voice pattern generated by the user and capturedby a microphone on the device; an image of a retina of a user's eyecaptured by the device; at least one fingerprint of the user captured bythe device; a palm scan of the user captured by the device; an image ofthe user captured by the device; a RFID tag tethered to the device; anda password.
 18. The system according to claim 16, wherein the initialsecondary identifier is the reference image of the user and secondaryidentifier is an image of the user's face captured by the device. 19.The system according to claim 15, further comprising a not verifiedmessage configured to be sent to the app if at least one of an outcomeof the image comparison algorithm is negative, or if an outcome of thelocation comparison algorithm is negative, if an outcome of the timecomparison is negative, or if the outcome of the device identificationcomparison algorithm is negative.
 20. The system according to claim 15,wherein the verification engine is configured to collect text from theidentification card, convert the text into the at least one piece ofdata and enter the at least one piece of data into a user profile.